Add role: Membarr #257
Add role: Membarr #257
Conversation
The code changes include the addition of Membarr's default variables and the creation/removal of Docker container directories, and creating the Docker container.
This commit adds a discord_token field to Membarr settings in defaults/settings.yml.default file. The configuration change enables users to set up their Discord bot token in Membarr.
This commit refactors the membarr application to use the default Discord token. The docker run command has been updated to include new environment variables, and the role's main task now checks for a specified default Discord token and fails when not specified.
|
should this be converted to a draft? |
|
so after figuring out how it works, I'll have to create docs for it regardless because its not documented well in the first place. anyone who decides to take a look at it, please lmk what you think, the container creates the either way, it works as intended right now, just gotta fill in relevant info in a file. |
|
@RaneyDazed Thanks for creating this role. I was able to test this, and it works as expected after adding 'plex_base_url = http://plex:32400' to the config.ini file. Setting up through discord channel added a weird long url to plex_base_url, I changed it to above and it worked fine. |
|
Make a template for the config file. For the Plex URL, use If the token can't be passed via the config file, use an env file instead of |
|
Is a template being made for this @RaneyDazed? |
|
will be messing with this in a bit! Sorry its taken so long. I forgot about it after I read the notification. |
- Added membarr_paths_recursive variable to allow recursive creation of directories in membarr role. - Added membarr_paths_config_location variable to specify the location of config.ini file in membarr role. - Created new subtask settings.yml to handle all the settings related tasks in membarr role. - Added import task to include the settings.yml subtask in the main tasks of membarr role. - Created config.ini.j2 template file to define the configuration options for membarr.
|
Still working on it, about done with the template and I'll test it out on a box or two. @keldian @maximuskowalski |
Well the template and subtask |
|
Should be all set..? |
|
Docs PR all that we need then and ready to go? |
|
Yup thats correct! although i was unaware it was waiting for a Docs pr before it would be approved. I'd have done that ages ago. I just didn't want to bother if it wasn't going to be approved. But I can write up some docs! |
|
Everything needs docs before it will be merged now. |
* Create Membarr Docker Container with Default Variables The code changes include the addition of Membarr's default variables and the creation/removal of Docker container directories, and creating the Docker container. * Add discord token to Membarr configuration in settings.yml.default This commit adds a discord_token field to Membarr settings in defaults/settings.yml.default file. The configuration change enables users to set up their Discord bot token in Membarr. * "Refactor membarr (main): Update default Discord token usage" This commit refactors the membarr application to use the default Discord token. The docker run command has been updated to include new environment variables, and the role's main task now checks for a specified default Discord token and fails when not specified. * feat: Add membarr_paths_recursive and membarr_paths_config_location - Added membarr_paths_recursive variable to allow recursive creation of directories in membarr role. - Added membarr_paths_config_location variable to specify the location of config.ini file in membarr role. - Created new subtask settings.yml to handle all the settings related tasks in membarr role. - Added import task to include the settings.yml subtask in the main tasks of membarr role. - Created config.ini.j2 template file to define the configuration options for membarr.
Description
Will create docs for it if it gets that far. I was hoping someone could give this a once over, as I'm struggling to figure out if I'm doing something wrong or if the bot/role itself is the problem.
How Has This Been Tested?
I've tested it on my home server and my feederbox. It connects fine to discord and the bot works and responds well. Everything looks good there. Only issue is it doesn't seem to want to connect to plex and I need someone or a few people to test it for me maybe? Thanks!